Constrained shortest path first for temporal tunnel services

ABSTRACT

An ingress node configured to receive a first request for a temporal label switched path (LSP) in the network. The first request indicates the ingress node, egress node, network constraint, and scheduled time interval having a predetermined start time and a predetermined end time for the temporal LSP to carry traffic. The ingress node computes a shortest path in the network for the temporal LSP that satisfies the network constraint in a shifted time interval when the request indicates that the time interval is elastic, and reserves a network resource for use during the shifted time interval for the temporal LSP in advance of the predetermined start time on a link extending from the ingress node to a next hop node on the path. The ingress node sends a path message to the next hop node to set up the temporal LSP in the shifted time interval.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. provisional patent applicationNo. 62/163,899, filed May 19, 2015 by Huaimo Chen et al., and titled“CSPF for Temporal Tunnel Services,” which is hereby incorporated byreference in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

Multiprotocol label switching (MPLS) is a data-carrying mechanism thatdirects data from one network node to a next network node based on pathlabels instead of network addresses, avoiding complex lookups in arouting table. The path labels identify virtual links or paths betweendistant nodes, rather than endpoints. MPLS may be used to carrydifferent kinds of traffic, including Internet protocol (IP) packets,asynchronous transfer mode (ATM) frames, synchronous optical networking(SONET) frames, and Ethernet frames. A constrained shortest path first(CSPF) algorithm is an advanced version of a shortest path algorithmused in open shortest path first (OSPF) and intermediate system tointermediate system (ISIS) route computations. CSPF is used in computinga shortest path for a label-switched path (LSP) based upon multipleconstraints. The CSPF algorithm considers a topology of a network,attributes of the LSP, and links in computing a path for the LSP.

SUMMARY

The problem in the prior art is that a network element computes ashortest path from a source to an egress that satisfies a given set ofconstraints without considering a time for which to reserve a networkresource for the path. The concepts disclosed herein solve this problemby configuring a network element to determine a shortest path from asource to the egress that satisfies the set of constraints for anelastic time interval.

In one embodiment, the disclosure includes ingress node in a network,comprising a receiver configured to receive a request for a temporallabel switched path (LSP) in the network, wherein the request indicatesthe ingress node, an egress node, a network constraint, and a scheduledtime interval having a predetermined start time and a predetermined endtime for the temporal LSP to carry traffic, a processor coupled to thereceiver and configured to compute a shortest path in the network forthe temporal LSP, wherein the path satisfies the network constraint in ashifted time interval when the request indicates that the time intervalis elastic, and reserve a network resource for use during the shiftedtime interval for the temporal LSP in advance of the predetermined starttime, wherein the network resource is reserved on a link extending fromthe ingress node to a next hop node on the path, and a transmittercoupled to the processor and configured to send a path message to thenext hop node to set up the temporal LSP in the network in the shiftedtime interval. In some embodiments, the disclosure also includes whereinreserving the network resource includes a future reservation, andwherein the network resource is reserved from a time-based trafficengineering link state database (TEDB), and/or wherein the requestcomprises a start time of the scheduled time interval, an end time ofthe scheduled time interval, and an elastic range upper bound, whereinthe elastic range upper bound is a pre-defined amount of time by whichthe elastic time interval is permitted to shift positively to a latertime than the start time, wherein the processor is further configured todetermine a first time that is between a first shift start time and theelastic range upper bound, and wherein the first shift start time is thestart time, wherein the first time is the only time between the firstshift start time and the first time that has a link in a TEDB thatsatisfies the network constraint in a first time interval from the firsttime for a duration from the start time to the end time, wherein fortimes between the first shift start time and the first time the linkdoes not satisfy the network constraint from each of the times for theduration, and/or wherein the processor is further configured todetermine the shortest path from the ingress node to the egress node inthe TEDB satisfying the network constraint in the first time intervalwhen the first time is found, and/or wherein when no path is found fromthe ingress node to the egress node in the TEDB satisfying the networkconstraint in the first time interval, the processor is furtherconfigured to determine a second time that is between a second shiftstart time and the elastic range upper bound, and wherein the secondshift start time is the first time, wherein the second time is the onlytime between the second shift start time and the second time that has alink in the TEDB that satisfies the network constraint in a second timeinterval from the second time for the duration from the start time tothe end time, and wherein for times between the second shift start timeand the second time the link does not satisfy the network constraintfrom each of the times for the duration, and determine the shortest pathfrom the ingress node to the egress node in the TEDB satisfying thenetwork constraint in the second time interval when the second time isfound, and/or wherein the request comprises a start time of thescheduled time interval, an end time of the scheduled time interval, andan elastic range lower bound, wherein the elastic range lower bound is apre-defined amount of time by which the elastic time interval ispermitted to shift negatively to an earlier time than the start time,wherein the processor is further configured to determine a third timethat is between the start time and the elastic range lower bound,wherein the third time is the only time between the start time and thethird time that has a link in a TEDB that satisfies the networkconstraint in a third time interval from the third time for a durationfrom the start time to the end time, and wherein for times between thethird time and the start time the link does not satisfy the networkconstraint from each of the times for the duration, and/or wherein therequest comprises a start time of the scheduled time interval, an endtime of the scheduled time interval, and an elastic range lower bound,and an elastic range upper bound, wherein the elastic range lower boundis a pre-defined amount of time by which the elastic time interval ispermitted to shift negatively to an earlier time than the start time,wherein the elastic range upper bound is a pre-defined amount of time bywhich the elastic time interval is permitted to shift positively to alater time than the start time, wherein the processor is furtherconfigured to compute a first time that is between the start time andthe elastic range upper bound, compute a second time that is between theelastic range lower bound and the start time, and determine a closertime of the first time and the second time, wherein the closer time is atime that is closer to the start time and has a link in a TEDB thatsatisfies the network constraint in a first time interval from thecloser time for a duration from the start time to the end time, andwherein for times between the start time and the closer time the linkdoes not satisfy the network constraint from each of the times for theduration, and/or wherein the request comprises a start time for the timeinterval and an elastic time range for the time interval, and whereinthe processor is further configured to compute the path for the LSP bydetermining a minimum amount of time to shift the time interval from thestart time such that the path satisfies the network constraint in theshifted time interval and the shifted time interval is positioned withinthe elastic time range, and initiate setup of the LSP in the shiftedtime interval to enable the LSP to carry traffic in the shifted timeinterval, and/or wherein the processor is further configured to initiatesetup of the LSP in the elastic time interval by sending, via thetransmitter, a Path message to a node along the path to initiate thecreation of the LSP at a beginning of the shifted time interval, andsending, via the transmitter, a path teardown (PathTear) message to anode along the path to initiate the deletion of the LSP at an end of theshifted time interval.

In another embodiment, the disclosure includes a method implemented in anetwork element (NE), comprising receiving, via a receiver, a requestrequesting creation of a temporal label switched path (LSP) in anetwork, wherein the request indicates an ingress, an egress, a networkconstraint, a scheduled time interval having an elastic range, apredetermined start time and a predetermined end time for the temporalLSP to carry first traffic in a shifted time interval within the elasticrange of the scheduled time interval, computing, via a processor, ashortest path for the temporal LSP by determining a minimum amount oftime to shift the scheduled time interval from the start time such thatthe path satisfies the network constraint in a shifted time interval andthe shifted time interval is positioned within the elastic time rangeand with the minimum time shift, determining, via the processor, whethera next hop link from the NE to a next downstream node on the shortestpath comprises a sufficient amount of network resources in the shiftedtime interval to satisfy the network constraint, and reserving, via theprocessor, the network resource on the next hop link for use during theshifted time interval for the temporal LSP in advance of thepredetermined start time according to the network constraint tofacilitate data forwarding for the temporal LSP in the shifted timeinterval when the next hop link from the NE to the next downstream nodeon the shortest path comprises the sufficient amount of networkresources in the shifted time interval to satisfy the networkconstraint. In some embodiments, the disclosure also includes sending,via the processor, a first Path message to itself, wherein the Pathmessage comprises the path, the network constraint, and the shifted timeinterval, receiving, via the processor, the first Path message,generating, via the processor, a second Path message according to thefirst Path message to indicate the shifted time interval, and sending,via a transmitter of the NE, the second Path message to the nextdownstream node to request the creation of the temporal LSP in thenetwork in the shifted time interval, and/or wherein the requestcomprises a start time of the scheduled time interval, an end time ofthe scheduled time interval, and an elastic range upper bound, whereinthe elastic range upper bound is a pre-defined amount of time by whichthe elastic time interval is permitted to shift positively to a latertime than the start time, wherein the method further comprisesdetermining a first time that is between a first shift start time andthe elastic upper bound, and wherein the first shift start time is thestart time, wherein the first time is the only time between the firstshift start time and the first time that has a link in a TEDB thatsatisfies the network constraint in a first time interval from the firsttime for a duration from the start time to the end time, and wherein fortimes between the first shift start time and the first time the linkdoes not satisfy the network constraint from each of the times for theduration, and/or wherein when no path is found from the ingress to theegress in the TEDB satisfying the network constraint in the first timeinterval, the method further comprises determining a second time that isbetween a second shift start time and the elastic range upper bound,wherein the second shift start time is the first time, wherein thesecond time is the only time between the second shift start time and thesecond time that has a link in the TEDB that satisfies the networkconstraint in a second time interval from the second time for theduration from the start time to the end time, and wherein for timesbetween the second shift start time and the second time the link doesnot satisfy the network constraint from each of the times for theduration, and determining the shortest path from the ingress to theegress in the TEDB satisfying the network constraint in the second timeinterval when the second time is found, and/or wherein the requestcomprises a start time of the scheduled time interval, an end time ofthe scheduled time interval, and an elastic range lower bound, whereinthe elastic range lower bound is a pre-defined amount of time by whichthe elastic time interval is permitted to shift negatively to an earliertime than the start time, wherein the method further comprisesdetermining a third time that is between the elastic range lower boundand the start time, wherein the third time is the only time between thethird time and the start time that has a link in TEDB that satisfies thenetwork constraint in a third time interval from the third time for athird duration from the start time to the end time, and wherein fortimes between the third time and the start time the link does notsatisfy the network constraint from each of the times for the duration,and determining the shortest path from the ingress to the egress in theTEDB satisfying the network constraint in the third time interval whenthe third time is found, and/or wherein the request comprises a starttime of the scheduled time interval, an end time of the scheduled timeinterval, and an elastic range lower bound, and an elastic range upperbound, wherein the elastic range lower bound is a pre-defined amount oftime by which the elastic time interval is permitted to shift negativelyto an earlier time than the start time, wherein the elastic range upperbound is a pre-defined amount of time by which the elastic time intervalis permitted to shift positively to a later time than the start time,wherein the method further comprises determining a first time that isbetween the start time and the elastic range upper bound, determining asecond time that is between the start time and the elastic range lowerbound, determining a closer time of the first time and the second time,wherein the closer time is a time that is closer to the start time andhas a link in a TEDB that satisfies the network constraint in a firsttime interval from the closer time for a duration from the start time tothe end time, and wherein for times between the start time and thecloser time the link does not satisfy the network constraint from eachof the times for the duration, and determining the shortest path fromthe ingress to the egress in the TEDB satisfying the network constraintin the first time interval when the first time is found.

In yet another embodiment, the disclosure includes an apparatus,comprising a receiver configured to receive a request requestingcreation of a temporal label switched path (LSP) in a network, whereinthe request indicates an ingress, an egress, a network constraint and ascheduled time interval having an elastic range, a predetermined starttime and a predetermined end time for the temporal LSP to carry trafficin a shifted time interval within the elastic range of the scheduledtime interval, a processor coupled to the receiver and configured tocompute a shortest path for the temporal LSP by determining a minimumamount of time to shift the scheduled time interval from the start timesuch that the path satisfies the network constraint in a shifted timeinterval and the shifted time interval is positioned within the elastictime range and with the minimum time shift, determine whether a next hoplink from the apparatus to a next downstream node on the shortest pathcomprises a sufficient amount of network resources in the shifted timeinterval to satisfy the network constraint, and reserve the networkresource on the next hop link for use during the shifted time intervalfor the temporal LSP in advance of a predetermined start time accordingto the network constraint to facilitate data forwarding for the temporalLSP in the shifted time interval. In some embodiments, the disclosurealso includes wherein the request further comprises a start time of thescheduled time interval, a stop time of the scheduled time interval, andan elastic upper range bound of the scheduled time interval, wherein theelastic range upper bound is a pre-defined amount of time by which theelastic time interval is permitted to shift positively to a later timethan the start time, wherein the processor is further configured todetermine a first time that is between a first shift start time and theelastic range upper bound, and wherein the first shift start time is thestart time, wherein the first time is the only time between the firstshift start time and the first time that has a link in a TEDB thatsatisfies the network constraint in a first time interval from the firsttime for a duration from the start time to the end time, and wherein fortimes between the first shift start time and the first time the linkdoes not satisfy the network constraint from each of the times for theduration, and/or wherein when no path is found from the ingress to theegress in the TEDB satisfying the network constraint in the first timeinterval, the processor is further configured to determine a second timethat is between a second shift start time and the elastic range upperbound, and wherein the second shift start time is the first time,wherein the second time is the only time between the second shift starttime and the second time that has a link in the TEDB that satisfies thenetwork constraint in a second time interval from the second time forthe duration from the start time to the end time, and wherein for timesbetween the second shift start time and the second time the link doesnot satisfy the network constraint from each of the times for theduration, and determine the shortest path from the ingress to the egressin the TEDB satisfying the network constraint in the second timeinterval when the second time is found, and/or wherein the requestfurther comprises a start time of the scheduled time interval, a stoptime of the scheduled time interval, and an elastic lower range bound ofthe scheduled time interval, wherein the elastic range lower bound is apre-defined amount of time by which the elastic time interval ispermitted to shift negatively to an earlier time than the start time,wherein the processor is further configured to determine a third timethat is between the elastic range lower bound and a third shift starttime, wherein the third shift start time is the start time, wherein thethird time is the only time between the third time and the start timethat has a link in a TEDB that satisfies the network constraint in athird time interval from the third time for a duration from the starttime to the stop time, and wherein for times between the third time andthe start time the link does not satisfy the network constraint fromeach of the times for the duration, and/or wherein when no path is foundfrom the ingress to the egress in the TEDB satisfying the networkconstraint in the third time interval, the processor is furtherconfigured to determine a fourth time that is between a fourth shiftstart time and the elastic range lower bound, wherein the fourth shiftstart time is the third time and the fourth time is the only timebetween the fourth shift start time and the fourth time that has a linkin the TEDB that satisfies the network constraint in a fourth timeinterval from the fourth time for the duration from the start time tothe stop time, wherein for times between the fourth shift start time andthe fourth time the link does not satisfy the network constraint fromeach of the times for the duration, and determine the shortest path fromthe ingress to the egress in the TEDB satisfying the network constraintin the fourth time interval when the fourth time is found.

For the purpose of clarity, any one of the foregoing embodiments may becombined with any one or more of the other foregoing embodiments tocreate a new embodiment within the scope of the present disclosure.

These and other features will be more clearly understood from thefollowing detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following brief description, taken in connection with theaccompanying drawings and detailed description, wherein like referencenumerals represent like parts.

FIG. 1 is a timing diagram of an embodiment of a time agnostic linkbandwidth profile.

FIG. 2 is a schematic diagram of an embodiment of a network thatprovides TTSs.

FIG. 3 is a schematic diagram of an embodiment of a NE.

FIG. 4 is a timing diagram of an embodiment of a time-based linkbandwidth profile.

FIG. 5 is a timing diagram of an embodiment of a temporal bandwidthreservation scheme with a recurrent time interval.

FIG. 6 is a timing diagram of an embodiment of a temporal bandwidthreservation scheme with an elastic time range.

FIG. 7 is a timing diagram of an embodiment of a temporal bandwidthreservation scheme with graceful periods.

FIG. 8 is a timing diagram of an embodiment of a link bandwidth profile.

FIG. 9A is a flowchart of an embodiment of a temporal LSP creationmethod.

FIG. 9B is a flowchart of an embodiment of a temporal LSP creationmethod with a positively elastic time range.

FIG. 9C is a flowchart of an embodiment of a temporal LSP creationmethod with a negatively elastic range.

FIG. 9D is a flowchart of an embodiment of a temporal LSP creationmethod with a positively and negatively elastic time range.

FIG. 10 is a flowchart of an embodiment of a temporal LSP creationmethod.

DETAILED DESCRIPTION

It should be understood at the outset that, although an illustrativeimplementation of one or more embodiments are provided below, thedisclosed systems and/or methods may be implemented using any number oftechniques, whether currently known or in existence. The disclosureshould in no way be limited to the illustrative implementations,drawings, and techniques illustrated below, including the exemplarydesigns and implementations illustrated and described herein, but may bemodified within the scope of the appended claims along with their fullscope of equivalent.

MPLS traffic engineering (MPLS TE) integrates traffic engineering (TE)capabilities into open system interconnection (OSI) model layer 3 (L3),which optimizes the routing of IP traffic, given the constraints imposedby backbone network capacity and topology. In a MPLS IF network, packetsare mapped to traffic flows, forwarding paths are computed based on thetraffic flow's resource requirement and available network resource, andtraffic flows are transported across the network using MPLS forwarding.Examples of a traffic flow's resource requirement may include bandwidthrequirements, latency tolerances, a priority versus other traffic flows,and a limit on the number of hops. In MPLS forwarding, paths arepredetermined and established for particular source-destination pairsinstead of forwarded on a hop-by-hop basis. The established paths arereferred to as LSPs or tunnels.

Although MPLS TE enables the establishment of resource-guaranteedend-to-end LSPs or tunnels, MPLS TE LSP tunnels are not time-aware. Oncean existing MPLS TE LSP tunnel is set up, the MPLS TE LSP tunnel isassumed to carry traffic indefinitely until the MPLS TE LSP tunnel isdown, for example, initiated by a tear down command or caused by a linkand/or node fault. When an MPLS TE LSP tunnel is established, it isassumed that the tunnel consumes its reserved network resources eventhough the tunnel may only use the reserved network resources for aperiod of time. As a result, tunnel service may not be scheduled inadvance.

FIG. 1 is a timing diagram of an embodiment of a time agnostic linkbandwidth profile 100. The x-axis represents time in some arbitraryconstant time units. The y-axis represents unreserved link bandwidth.The profile 100 shows the amount of unreserved bandwidth, denoted as B0,from the current time T0 to an indefinite end time or until there is achange to the unreserved bandwidth such as the occurrence of a nextbandwidth reservation. The profile 100 does not track unreservedbandwidth by time intervals or on a time-period basis. Thus, the profile100 is not suitable for tunnel service scheduling, which requiresbandwidth reservation in advance of time intervals scheduled for a LSPto carry traffic.

Disclosed herein are various embodiments for establishing temporal LSPtunnels. A temporal LSP tunnel is a tunnel that is scheduled forcarrying traffic in one or more predetermined time intervals. Forexample, many tunnel services are planned and scheduled. The disclosedembodiments provide mechanisms for reserving network resources fortemporal tunnels during certain time intervals in advance. Thus, thedisclosed embodiments enable efficient usage of network resources andallow internet service providers (ISPs) to provide service schedulingand/or service calendaring. In an embodiment, a network administrator ora user configures an ingress node of a temporal LSP with a time scheduleand a network constraint for the temporal LSP to carry traffic. A timeschedule may comprise one or more pre-determined time intervals eachcomprising a definite duration. The ingress node computes a shortestpath in the network for the temporal LSP satisfying the networkconstraint in each time interval. The ingress node initiates thecreation of the temporal LSP in a downstream direction. For example, aresource reservation protocol for traffic engineering (RSVP-TE) Pathmessage is send to each node on the path. The Path message includes astart time of the time interval, a stop time of the time interval, and aconstraint. Each node checks the availability of network resources inthe each time interval that satisfies the constraint. When the Pathmessage reaches an egress node of the temporal LSP, the egress nodeinitiates an in-advance reservation of network resource for the temporalLSP in an upstream direction. For example, a RSVP-TE reserve (Resv)message is sent to each node on the path. Each node reserves networkresource in advance for the temporal LSP in each time interval on a nexthop link to a next downstream node on the path when receiving the Resvmessage. Downstream refers to the direction from an ingress to adestination, whereas upstream refers to the direction from a destinationto a source. To tear down the temporal LSP, a requesting entity sendsthe ingress node a request. The requesting entity may be a networkadministrator, a user, an application, a switch, and a router. Theingress node initiates the tear down of the temporal LSP in a downstreamdirection, where a RSVP-TE PathTear message is sent to each node on thepath. In one embodiment, each node reserves the network resource for afuture reservation, but does not reserve a reservation for the networkresource at a current time when the reservation is made. In oneembodiment, each node releases the in advance reserved network resourcein remaining time intervals that have not elapsed. Although thedisclosed embodiments describe the in advance resource reservationmechanism in the context of bandwidths, the disclosed embodiments aremay be applied to reserve any network resource in advance.

FIG. 2 is a schematic diagram of an embodiment of a MPLS network 200that provides TTSs. The network 200 comprises a plurality of edge nodes221 and a plurality of internal nodes 222 interconnected by a pluralityof communication links 230, 231, 232, and 233. The edge nodes 221 areshown as PE1, PE2, PE3, and PE4. The edge nodes 221 are located at anedge or a boundary of the network 200 and may be coupled to one or morenodes that are located outside the network 200. The internal nodes 222are shown as P1, P2, P3, and P4. The internal nodes 222 are locatedwithin the network 200. The underlying physical network of the network200 may be any type of transport network such as an electrical networkand/or an optical network. The communication links 230-233 may comprisephysical links such as fiber optic links, electrical links, wirelesslinks and/or logical links used to transport data in the network 200.The network 200 may operate under a single network administrative domainor multiple network administrative domains. In an embodiment, thenetwork 200 employs a MPLS forwarding data plane.

The edge nodes 221 and the internal nodes 222 are network devicesconfigured to perform TTS operations in the network 200. Some examplesof TTS operations include computing paths for temporal LSPs that arescheduled to carry traffic in scheduled time intervals, reservingnetwork resource on the links 230-233 that are along the computed pathsfor the temporal LSPs in advance of the scheduled time intervals,setting up and tearing down temporal LSPs, and maintaining anddistributing time-based TE information, as described more fully below. ALSP is a predetermined route between a source-destination pair andidentified by path labels. A temporal LSP is a scheduled LSP, wherenetwork resources are reserved in advance on links 230-233 along a pathof the temporal LSP according to scheduled time intervals.

As an example, the network 200 is configured with a temporal LSP 250that is scheduled to transport data traffic for a data flow between asource 241 and a destination 242 according to a given time schedule. Thesource 241 is any network device configured to generate data for thedata flow. The destination 242 is any network device configured toconsume the data of the data flow. The temporal LSP 250 extends from theedge node PE1 221 to the edge node PE4 221, traversing through theinternal nodes P1 and P2 222. The edge node PE1 221 that receives datatraffic from the source 241 external to the network 200 and sends datatraffic using the temporal LSP 250 in the network 200 is referred to asan ingress node of the temporal LSP 250. The edge node PE4 221 thatreceives data traffic from the temporal LSP 250 in the network 200 andsends data traffic to the destination 242 outside of the network 200 isreferred to as an egress node of the temporal LSP 250. The internalnodes P1 and P2 222 located along a path of the temporal LSP 250 betweenthe ingress node and the egress node are referred to as transit nodes ofthe temporal LSP 250. The direction from the source 241 to thedestination 242 is referred to as downstream. The direction from thedestination 242 to the source 241 is referred to as upstream.

In an embodiment, a requesting entity configures the edge node PE1 221,which is the ingress node of the temporal LSP 250, with a time scheduleand a network constraint for the LSP 250. The requesting entity may be anetwork administrator, a user, an application, a switch, and a router.The time schedule comprises a series of time intervals each having apredetermined start time and a predetermined end time. Upon receivingthe configuration, the edge node PE1 221 computes a shortest path in thenetwork for the temporal LSP 250 satisfying the network constraint ineach time interval. The edge node PE1 221 initiates the creation of thetemporal LSP 250 in a downstream direction. To create the temporal LSP250, each node on the path, including the edge node PE1 221 and theinternal nodes P1 and P2 222, reserves a network resource in advance ona next hop link for the temporal LSP 250 in each time interval based onthe network constraint. For example, the edge node PE1 221, the internalnode P1 222, and the internal node P2 222 reserve network resources onthe link 231, 232, and 233 in each time interval based on the networkconstraint, respectively. After reserving the network resources, each ofthe edge node PE1 221 and the internal nodes P1 and P2 222 tracks andupdates remaining available or unreserved network resource oncorresponding links 231-233 in each time interval, for example, in aTEDB, and distributes the updated unreserved network resourceinformation to other edge nodes 221 and other internal nodes 222. In anembodiment, OSPF TE LSAs are extended to enable distribution oftime-based TE information in the network 200. It should be noted that insome embodiments, updated unreserved network resource information isdistributed when there is a significant change in the amount ofunreserved network resource, for example, based on a predeterminedthreshold.

To facilitate subsequent data forwarding, the edge node PE4 221, theinternal node P2 222, and the internal node P1 222 allocates a firstlabel, a second label, and a third label, respectively, and notifies anext upstream node of a corresponding label. Subsequently, uponreceiving a packet from the source 241, the edge node PE1 221 attachesthe third label to the packet and forwards the packets to a nextdownstream node, which is the internal node P1 222, along the link 231.When the internal node P1 222 receives the packet, the internal node P1222 swaps the third label with the second label and forwards the packetto a next downstream node, which is the internal node P2 222, along thelink 232. When the internal node P2 222 receives the packet, theinternal node P2 222 swaps the second label with the first label andforwards the packet to a next downstream node, which is the edge nodePE4 221, along the link 233. When the edge node PE4 221 receives thepacket, the edge node PE4 221 removes the first label and forwards thepacket to the destination 242.

To tear down the temporal LSP 250, the network administrator or the usersends the edge node PE1 221 a tear-down request. The edge node PE1 221initiates the tear down of the temporal LSP 250 in a downstreamdirection. Each node on the path, including the edge node PE1 221 andthe internal nodes P1 and P2 222, releases the in advance reservednetwork resource in remaining time intervals that have not elapsed. Itshould be noted that although the reservation and distribution oftime-based network resource are described in the context of MPLStunnels, the network 200 may be alternatively configured as determinedby a person of ordinary skill in the art to achieve similarfunctionalities.

FIG. 3 is a schematic diagram of an embodiment of an NE 300, such asedge nodes 221, the internal nodes 222, the source 241, and thedestination 242 in a network such as the network 200. NE 300 may beconfigured to implement and/or support temporal tunnel creation anddeletion mechanisms and schemes described herein. NE 300 may beimplemented in a single node or the functionality of NE 300 may beimplemented in a plurality of nodes. One skilled in the art willrecognize that the term NE encompasses a broad range of devices of whichNE 300 is merely an example. NE 300 is included for purposes of clarityof discussion, but is in no way meant to limit the application of thepresent disclosure to a particular NE embodiment or class of NEembodiments.

At least some of the features/methods described in the disclosure areimplemented in a network apparatus or component such as an NE 300. Forinstance, the features/methods in the disclosure may be implementedusing hardware, firmware, and/or software installed to run on hardware.The NE 300 is any device that transports packets through a network,e.g., a switch, router, bridge, server, a client, etc. As shown in FIG.3, the NE 300 comprises transceivers (Tx/Rx) 310, which may betransmitters, receivers, or combinations thereof. The Tx/Rx 310 iscoupled to a plurality of ports 320 for transmitting and/or receivingframes from other nodes.

A processor 330 is coupled to each Tx/Rx 310 to process the framesand/or determine which nodes to send the frames to. The processor 330may comprise one or more multi-core processors and/or memory devices332, which may function as data stores, buffers, etc. The processor 330may be implemented as a general processor or may be part of one or moreapplication specific integrated circuits (ASICs) and/or digital signalprocessors (DSPs).

The processor 330 comprises a temporal LSP processing module, which mayperform path calculations according to the time-based TE information andmay comprise means to implement the functional steps in methods 900 and1300, as discussed more fully below, and/or any other flowcharts,schemes, and methods discussed herein. As such, the inclusion of thetemporal LSP processing module 333 associated methods and systemsprovide improvements to the functionality of the NE 300. Further, thetemporal LSP processing module 333 effects a transformation of aparticular article (e.g., the network) to a different state. In analternative embodiment, the temporal LSP processing module 333 may beimplemented as instructions stored in the memory device 332, which maybe executed by the processor 330.

The memory device 332 may comprise a cache for temporarily storingcontent, e.g., a random-access memory (RAM). Additionally, the memorydevice 332 may comprise a long-term storage for storing contentrelatively longer, for example, a read-only memory (ROM). For instance,the cache and the long-term storage may include dynamic RAMs (DRAMs),solid-state drives (SSDs), hard disks, or combinations thereof. Thememory device 332 may be configured to store one or more time-basedTEDBs 334, as discussed more fully below.

It is understood that by programming and/or loading executableinstructions onto the NE 300, at least one of the processor 330 and/ormemory device 332 are changed, transforming the NE 300 in part into aparticular machine or apparatus, e.g., a multi-core forwardingarchitecture, having the novel functionality taught by the presentdisclosure. It is fundamental to the electrical engineering and softwareengineering arts that functionality that can be implemented by loadingexecutable software into a computer can be converted to a hardwareimplementation by well-known design rules. Decisions betweenimplementing a concept in software versus hardware typically hinge onconsiderations of stability of the design and numbers of units to beproduced rather than any issues involved in translating from thesoftware domain to the hardware domain. Generally, a design that isstill subject to frequent change may be preferred to be implemented insoftware, because re-spinning a hardware implementation is moreexpensive than re-spinning a software design. Generally, a design thatis stable and that will be produced in large volume may be preferred tobe implemented in hardware, for example in an ASIC, because for largeproduction runs the hardware implementation may be less expensive thanthe software implementation. Often a design may be developed and testedin a software form and later transformed, by well-known design rules, toan equivalent hardware implementation in an ASIC that hardwires theinstructions of the software. In the same manner as a machine controlledby a new ASIC is a particular machine or apparatus, likewise a computerthat has been programmed and/or loaded with executable instructions(e.g., a computer program product stored in a non-transitorymedium/memory) may be viewed as a particular machine or apparatus.

FIG. 4 is a timing diagram of an embodiment of a time-based linkbandwidth profile 400. The x-axis represents time in some arbitraryconstant time units. The y-axis represents unreserved bandwidth. Theprofile 400 corresponds to time-based TE information maintained by theedge nodes 221, the internal nodes 222, and the NE 300, for example, ina time-based TEDB such as the time-based TEDB 334. The profile 400 showsunreserved bandwidth at a certain priority level on a link such as thelinks 230-233 in a network such as the network 200 as a function oftime, which includes a series of time intervals 421, 422, 423, and 424.As shown, the amount of unreserved bandwidth 431 at the time interval421 from a time 410, denoted as T₀, to a time 411, denoted as T₁, is B₀.The amount of unreserved bandwidth 432 at the time interval 422 from thetime 411 to a time 412, denoted as T₂, is B₁. The amount of unreservedbandwidth 433 at the time interval 423 from the time 412 to a time 413,denoted as T₃, is B₂. The amount of unreserved bandwidth 434 at the timeinterval 424 from the time 413 to a time 414, denoted as T₄, is B₃.

In one embodiment, the profile 400 is recorded in a time-based TEDBusing absolute time as shown below:

-   -   [T₀, B₀], [T₁, B₁], [T₂, B₂], [T₃, B₃],        where T₀, T₁, T₂, and T₃ are global clock times in the network        synchronized among all nodes in the network.

In another embodiment, the profile 400 is recorded in a time-based TEDBusing relative time as shown below:

-   -   [P₀, B₀], [P₁, B₁], [P₂, B₂], [P₃, B₃],        where P₀, P₁, P₂, and P₃ represent durations of the time        intervals 421, 422, 423, and 424, respectively, and P₀ begins at        a current time T₀. When using relative time representations, a        node may use a local clock time, which may be different from        another node in the network. One approach to implementing the        profile 400 is to configure a timer to expire at a unit time        (e.g., at every second) and use a period variable, denoted as P,        to track the expiration of the time intervals 421-424. For        example, at time 410, P is set to a duration or a period (e.g.,        P₀) of the time interval 421 according to the unit time. When        the timer expires, P is decremented by the unit time and the        duration or period (e.g., P₀) of a corresponding time interval        in the time-based TEDB is updated by P. The expiration of the        timer indicates the unit time has elapsed. When P reaches a        value of 0, P is set to a duration or a period (e.g., P₁) of a        next time interval, which is the time interval 422.

In some other embodiments, the profile 400 is recorded in a time-basedTEDB using a combination of absolute time and relative time as shownbelow:

-   -   T₀, [P₀, B₀], [P₁, B₁], [P₂, B₂], [P₃, B₃],        where P₀, P₁, P₂, and P₃ represent durations of the time        intervals 421, 422, 423, and 424, respectively, and T₀        represents a start time of the series of time intervals 421-424.        The time T₀ is an absolute time, which is a global clock time of        the network synchronized among all nodes in the network

FIG. 5 is a timing diagram of an embodiment of a temporal bandwidthreservation scheme 500. In the scheme 500, the x-axis represents time insome arbitrary units of time and the y-axis represents bandwidth in somearbitrary units of bandwidth. The scheme 500 is implemented by an NEsuch as the edge nodes 221, the internal nodes 222, and the NE 300 toreserve a bandwidth for an LSP, such as the LSP 150. For example, at acurrent time 501, denoted as T₀, a requesting entity may send a requestmessage to a NE to request path computation for an LSP in a timeinterval 520 according to certain network constraints including aconstraint for a bandwidth 530 in an amount of B. The requesting entitymay be a network administrator, a user, an application, a switch, and arouter. In response to the request message, the NE computes a path forthe LSP satisfying the network constraints and reserves the bandwidth530 for the LSP in the requested time interval 520. Subsequently, theLSP is configured is to carry traffic in the time interval 520. Asshown, the time interval 520 starts at a time 511, denoted as T_(a), andends at a time 512, denoted as T_(b). Thus, a time schedule for thescheme 500 may be represented as [T_(a), T_(b)]. A time schedule may beincluded in the request message by indicating an absolute time for thetime 511, an absolute time for the time 512, a relative time for thetime 511, a relative time for the time 512, a duration of the timeinterval 520, or combinations thereof, as described more fully below. Itshould be noted that although the scheme 500 illustrates schedulingmechanisms for bandwidth reservation, the scheme 500 may be employed forreserving other types of network resources, such as wavelengths, for theLSP.

FIG. 6 is a timing diagram of an embodiment of a temporal bandwidthreservation scheme 600 with an elastic time range that is permitted toshift to positively by a pre-defined amount. In the scheme 600, thex-axis represents time in some arbitrary units of time and the y-axisrepresents bandwidth in some arbitrary units of bandwidth. The scheme600 is implemented by an NE such as the edge nodes 221, the internalnodes 222, and the NE 300 to reserve a bandwidth for an LSP, such as theLSP 150. The scheme 600 is similar to the scheme 500, but reservesbandwidth in a time interval 620 with a positively elastic time rangethat is permitted to shift positively to the right by a pre-definedamount. For example, at a current time 601, denoted as T₀, therequesting entity may send a request message to a NE to request pathcomputation for an LSP in a time interval 620 with a positively elastictime range according to certain network constraints including aconstraint for a bandwidth 630 in an amount of B. The positively elastictime range may be represented by an elastic range upper bound 652,denoted as P. For example, the elastic range upper bound 652 maycomprise time durations of about 300 seconds. In response to the requestmessage, the edge node may compute a path for the LSP satisfying thebandwidth 630 constraint and reserves a bandwidth 630 for the LSP asclose to the requested time interval 620 as possible bounded by theelastic range upper bound 652. Subsequently, the LSP is configured tocarry traffic in a shifted time interval 660. As shown, the requestedtime interval 620 spans a time duration between a time 612, denoted asT_(a), and a time 614, denoted as T_(b). However, the scheme 600 allowsthe bandwidth to be reserved ending at a time 616, denoted as T_(b)+P.As shown, a bandwidth 630 is reserved between a shifted start time 613,denoted as T_(a)+x, and a shifted end time 615, denoted as T_(b)+x,where x satisfies the elastic range upper bound 652. Thus, a timeschedule for the scheme 600 may be represented as shown below:

-   -   [T_(a)+x, T_(b)+x],        where 0≤x≤P and x represents a minimum amount of time from 0 to        P that is required to shift requested time interval 620 to the        right to satisfy the requested constraints.

The requesting entity may include the time schedule in the requestmessage by indicating an absolute time for the time 612, an absolutetime for the time 614, a relative time for the time 612, a relative timefor the time 614, a duration of the interval 620, a duration of theelastic range upper bound 652 (P), or combinations thereof, as describedmore fully below. It should be noted that although the scheme 600illustrates scheduling mechanisms for bandwidth reservation, the scheme600 may be employed for reserving other types of network resources, suchas wavelengths, for LSPs.

FIG. 7 is a timing diagram of an embodiment of a temporal bandwidthreservation scheme 700 with an elastic time range that is permitted toshift to the left by a pre-defined amount. In the scheme 700, the x-axisrepresents time in some arbitrary units of time and the y-axisrepresents bandwidth in some arbitrary units of bandwidth. The scheme700 is implemented by an NE such as the edge nodes 221, the internalnodes 222, and the NE 300 to reserve a bandwidth for an LSP, such as theLSP 150. The scheme 700 is similar to the scheme 600, but reservesbandwidth in a time interval 720 with a negatively elastic time rangethat is permitted to shift negatively by a pre-defined amount. Forexample, at a current time 701, denoted as T₀, the requesting entity maysend a request message to an NE to request path computation for an LSPin a time interval 720 with a negatively elastic time range according tocertain network constraints including a constraint for a bandwidth 730in an amount of B. The negatively elastic time range may be representedby an elastic range lower bound 751, denoted as P. For example, theelastic range lower bound 751 may comprise time durations of about 300seconds. In response to the request message, the edge node may compute apath for the LSP satisfying the bandwidth 730 constraint and reserves abandwidth 730 for the LSP as close to the requested time interval 720 aspossible bounded by the elastic range lower bound 751. Subsequently, theLSP is configured to carry traffic in a shifted time interval 760. Asshown, the requested time interval 720 spans a time duration between atime 712, denoted as T_(a), and a time 714, denoted as T_(b). However,the scheme 700 allows the bandwidth to be reserved beginning at a time711, denoted as T_(a)−P. As shown, a bandwidth 730 is reserved between ashifted start time 713, denoted as T_(a)+x, and a shifted end time 715,denoted as T_(b)+x, where x satisfies the elastic range lower bound 751.Thus, a time schedule for the scheme 700 may be represented as shownbelow:

-   -   [T_(a)+x, T_(b)+x],        where −P≤x≤0 and x represents a minimum amount of time from −P        to 0 that is required to shift requested time interval 720 in        order to satisfy the requested constraints.

The requesting entity may include the time schedule in the requestmessage by indicating an absolute time for the time 712, an absolutetime for the time 714, a relative time for the time 712, a relative timefor the time 714, a duration of the time interval 720, a duration of theelastic range lower bound 751 (P) or combinations thereof, as describedmore fully below. It should be noted that although the scheme 700illustrates scheduling mechanisms for bandwidth reservation, the scheme700 may be employed for reserving other types of network resources, suchas wavelengths, for LSPs.

FIG. 8 is a timing diagram of an embodiment of a temporal bandwidthreservation scheme 800 with an elastic time range that is permitted toshift to the left and right by a pre-defined amount. In the scheme 800,the x-axis represents time in some arbitrary units of time and they-axis represents bandwidth in some arbitrary units of bandwidth. Thescheme 800 is implemented by an NE such as the edge nodes 221, theinternal nodes 222, and the NE 300 to reserve a bandwidth for an LSP,such as the LSP 150. The scheme 800 is similar to the schemes 600 and700, but reserves bandwidth in a time interval 820 with a negatively andpositively elastic time range that is permitted to shift negatively andpositively by a pre-defined amount. For example, at a current time 801,denoted as T₀, a requesting entity may send a request message to an NEto request path computation for an LSP in a time interval 820 with anegatively and/or positively elastic time range according to certainnetwork constraints including a constraint for a bandwidth 830 in anamount of B. The negatively elastic time range may be represented by anelastic range lower bound 851, denoted as P, and the positively elastictime range may be represented by an elastic range upper bound 852,denoted as Q. For example, the elastic range lower bound 851 and theelastic range upper bound 852 may comprise time durations of about 300seconds. In response to the request message, the NE computes a path forthe LSP satisfying the bandwidth 830 constraint and reserves a bandwidth830 for the LSP as close to the requested time interval 820 as possiblebounded by the elastic range lower bound 851 and the elastic range upperbound 852. Subsequently, the LSP is configured to carry traffic in ashifted time interval 860. As shown, the requested time interval 820spans a time duration between a time 812, denoted as T_(a), and a time814, denoted as T_(b). However, the scheme 800 allows the bandwidth tobe reserved beginning at a time 811, denoted as T_(a)−P, or ending at atime 816, denoted as T_(b)+Q. As shown, a bandwidth 830 is reservedbetween a shifted start time 813, denoted as T_(a)+x, and a shifted endtime 815, denoted as T_(b)+x, where x satisfies the elastic range lowerbound 851 and the elastic range upper bound 852. Thus, a time schedulefor the scheme 800 may be represented as shown below:

-   -   [T_(a)+X, T_(b)+X],        where −P≤x≤Q and x represents a minimum amount of time from −P        to Q that is required to shift requested time interval 820 in        order to satisfy the requested constraints.

The requesting entity may include the time schedule in the requestmessage by indicating an absolute time for the time 812, an absolutetime for the time 814, a relative time for the time 812, a relative timefor the time 814, a duration of the time interval 820, a duration of theelastic range lower bound 851, a duration of the elastic range upperbound 852, or combinations thereof, as described more fully below. Itshould be noted that although the scheme 800 illustrates schedulingmechanisms for bandwidth reservation, the scheme 800 may be employed forreserving other types of network resources, such as wavelengths, forLSPs.

FIGS. 9A-D are flowcharts of an embodiment of a temporal tunnel servicemethod 900. The method 900 is implemented by an NE such as the edgenodes 221, the internal nodes 222, and the NE 300. The method 900 isimplemented when creating a temporal LSP, such as LSP 150, according toa given time interval. At step 905, a request for creating a temporalLSP in a time interval is received, for example, from a requestingentity. The temporal LSP may be a P2P LSP or a P2MP LSP. The request mayindicate an ingress node such as edge node 221 PE1, an egress node suchas edge node 221 PE4, a time interval from a first time, such as thetimes 511, 612, 712, and 812, to a second time, such as the times 512,614, 714, and 814. The start time and/or the end time may be representedas absolute times and/or relative times. In addition, the request mayindicate an elastic range with an elastic range lower bound, such as theelastic range lower bounds 751 and 851, and an elastic range upperbound, such as the elastic range upper bounds 652 and 852.

At step 907, a shortest path from the ingress node to the egress node ina network, such as the network 200, satisfying a constraint in the timeinterval is computed, for example, by employing a CSPF algorithm. Theconstraint may include bandwidth, wavelengths, delays, QoS, and numberof hops. For example, the NE is configured to compute paths in a singleAS domain, such as the domains 240. Thus, the computed shortest path mayspan a segment of the LSP within the AS domain of the NE. When the timeinterval is a recurrent time interval, the shortest path is computedsuch that the shortest path satisfies the constraint in each recurringtime interval.

At decision diamond 910, it may be determined whether a path is foundfrom the ingress node to the egress node in the network. For example,the NE may be configured to determine whether a path is found from theingress node to the egress node in the time interval. At block 915, if apath is found that satisfies the constraints and the time interval, thepath and an indication that the path has been found may be returned. Forexample, the NE may notify the requesting entity that a path satisfyingthe constraints within the time interval has been found. A bandwidth maybe reserved for the LSP along the shortest path found in the timeinterval. The bandwidth is reserved from a TEDB on each of the linksalong the shortest path computed for the LSP.

At decision diamond 920, if a path is not found that satisfies theconstraints within the time interval, then it may be determined whetherthe time interval is elastic. For example, the NE may determine whetherthe time interval is elastic based on the request, which includes anindication of an elastic time range. At block 925, if it is determinedthat the time interval is not elastic, then an indication that a pathcannot be found may be returned. For example, the NE may determinewhether the request indicates an elastic range upper bound or an elasticrange lower bound. If the request does not indicate either an elasticrange upper bound or an elastic range lower bound, the NE may notify therequesting entity that a path satisfying the constraints within the timeinterval has not been found.

At decision diamond 940, it may be determined whether the time intervalis only positively elastic within an elastic range upper bound. Forexample, the NE may determine that the request only indicates an elasticrange upper bound. In this case, the method proceeds to circle A, whichis described below in more detail with regard to FIG. 9A below. If it isdetermined that the time interval is not solely positively elastic, atdecision diamond 950, it may be determined whether the time interval isonly negatively elastic within an elastic range lower bound. Forexample, the NE may determine that the request only indicates an elasticlower range bound. In this case, the method proceeds to circle B, whichis described in more detail below with regard to FIG. 9B. If it isdetermined that the time interval is not solely positively elastic orsolely negatively elastic, at decision diamond 960, it may be determinedwhether the time interval is positively and negatively elastic with anelastic range upper bound and an elastic range lower bound. For example,the NE may determine that the request indicates both an elastic rangeupper bound and an elastic range lower bound. In this case, the methodproceeds to circle C, which is described in more detail below withregard to FIG. 9C.

At block 1005 of FIG. 9B, the start time T_(a) is assigned to a shiftstart time T₀. At block 1010, a smallest time (T) that is greater thanthe shift start time To and less than or equal to the elastic rangeupper bound (T_(a)+P), such as the elastic range upper bound 652, forwhich there is a link in the TEDB that satisfies the constraints in thetime interval from T to T+(T_(b)−T_(a)) and does not satisfy theconstraints in a time interval from T₁ to T₁+(T_(b)−T_(a)) for any time(T₁) from T₀<T₁<T is determined. The smallest time T may be representedas T₀<T<=T_(a)+P. The smallest time T is the time that is the closest tothe requested time interval that satisfies the network constraints. Thetimes that are greater than the shift start time and less than thesmallest time T do not satisfy network constraints. For example, the NEmay traverse all the links in the TEDB and find a smallest time L_(i)for each of the links that satisfies the network constraints such as thebandwidth constraint in the time interval from L_(i) toL_(i)+(T_(b)−T_(a)) and does not satisfy the network constraints such asthe bandwidth constraint in the time interval from K_(i) toK_(i)+(T_(b)−T_(a)) for any K_(i) from T₀<K_(i)<L_(i). The smallest timeT is the smallest one among all L_(i).

At decision diamond 1020, it is determined whether a smallest time T isfound within the positively elastic time range. For example, the NE maycompute a smallest time within the positively elastic time range thatsatisfies the network constraints. At block 1030, if it is determinedthat a time within the positively elastic time range that satisfies thenetwork constraints does not exist, then an indication that a pathcannot be found is returned. For example, if the NE cannot determine atime within the positively elastic time range that satisfies the networkconstraints, then the NE notifies the requesting entity that a pathcannot be found. The NE may send a path computation response to therequesting entity indicating that a path for the LSP satisfying thenetwork constraint in the scheduled time interval cannot be found.

If the smallest time T is found, then at block 1050, a shortest path ina network, such as the network 200, from the ingress node to the egressnode satisfying the requested constraints in the time interval from T toT+(T_(b)−T_(a)) is computed, for example, by employing a CSPF algorithm.The constraint may include bandwidth, wavelengths, delays, QoS, andnumber of hops. For example, the NE is configured to compute paths in asingle AS domain, such as the domains 240. Thus, the computed shortestpath may span a segment of the LSP within the AS domain of the NE.

At decision diamond 1060, it may be determined whether a shortest pathin the network that satisfies the requested constraints in the timeinterval from T to T+(T_(b)−T_(a)) is found. At block 1070, a path maybe successfully computed, and the smallest time T and an indication ofthe path may be returned. For example, the NE may successfully find theshortest path in the network that satisfies the requested constraints.The NE may notify the requesting entity of the computed shortest pathand the smallest time T. From the time T, the time interval from T toT+(T_(b)−T_(a)) is obtained, which is called a shifted time interval.For example, the NE may transmit a path computation response to therequesting entity indicating a path for the LSP satisfying the networkconstraint in the shifted time interval and an in-advance reservation ofnetwork resource along the path for the LSP in the shifted timeinterval. At block 1065, no path can be computed in the network thatsatisfies the requested constraints in the time interval from T toT+(T_(b)−T_(a)). In this case, the smallest time T found is assigned tothe shift start time To. With this new shift start time, the methodreturns to block 1010 and repeats the steps in blocks 1010-1030 or1010-1070 until the method reaches block 1070 or block 1030.

At block 1105 of FIG. 9C, the start time T_(a) is assigned to a shiftstart time T₀. At block 1110, a biggest time (T) that is greater thanelastic range lower bound and less than the shift start time, for whichthere is a link in the TEDB that satisfies the constraints in the timeinterval from T to T+(T_(b)−T_(a)) and does not satisfy the constraintsin a time interval from T₁ to T₁+(T_(b)−T_(a)) for any time (T₁) fromT<T₁<T₀ is determined. The biggest time T may be represented asT_(a)−P<=T<T₀. That is, the biggest time T is the time that is theclosest the requested time interval that satisfies the networkconstraints. The times that are greater than T do not satisfy thenetwork constraints. For example, the NE may traverse all the links inthe TEDB and find a biggest time L_(i) for each of the links thatsatisfies the constraints such as the bandwidth constraint in the timeinterval from L_(i) to L_(i)+(T_(b)−T_(a)) and does not satisfy theconstraints such as the bandwidth constraint in the time interval fromK_(i) to K_(i)+(T_(b)−T_(a)) for any K_(i) from L_(i)<K_(i)<T₀. Thebiggest time T is the biggest one among all L_(i).

At decision diamond 1120, it is determined whether a biggest time T isfound within the negatively elastic time range. At block 1130, if it isdetermined that a time within the negatively elastic time range thatsatisfies the constraints does not exist, then an indication that a pathcannot be found is returned. For example, if the NE cannot determine atime within the negatively elastic time range that satisfies the networkconstraints, then the NE notifies the requesting entity that a pathcannot be found.

At block 1150, a shortest path in a network, such as the network 200,from the ingress node to the egress node satisfying the constraints inthe time interval from T to T+(T_(b)−T_(a)) is computed, for example, byemploying a CSPF algorithm. The constraint may include bandwidth,wavelengths, delays, QoS, and number of hops. For example, the NE isconfigured to compute paths in a single AS domain, such as the domains240. Thus, the computed shortest path may span a segment of the LSPwithin the AS domain of the NE.

At decision diamond 1160, it may be determined whether a shortest pathin the network that satisfies the requested constraints in the timeinterval from T to T+(T_(b)−T_(a)) is found. At block 1070, a path maybe successfully computed, and the biggest time T and an indication ofthe path may be returned. For example, the NE may successfully find theshortest path in the network that satisfies the requested constraints.The NE may notify the requesting entity of the computed shortest pathand the biggest time T. From the time T, the shifted time interval fromT to T+(T_(b)−T_(a)) is obtained. For example, the NE may transmit apath computation response to the requesting entity indicating a path forthe LSP satisfying the network constraint in the shifted time intervaland an in-advance reservation of network resource along the path for theLSP in the shifted time interval. At block 1165, no path can be computedin the network that satisfies the requested constraints in the timeinterval from T to T+(T_(b)−T_(a)). In this case, the biggest time Tfound is assigned to the shift start time To. With this new shift starttime, the method returns to block 1110 and repeats the steps in block1110-1130 or 1110-1170 until the method reaches block 1170 or block1130.

At block 1205 of FIG. 9D, the start time T_(a) is assigned to a shiftleft start time To and shift right start time T₁. At block 1210, abiggest time T_(c) may be determined in a manner similar to which isdescribed with regard to block 1110, which is directed to determining abiggest time in a negatively elastic time interval. The biggest timeT_(c) may be represented as (T_(a)−P)<=T_(c)<T₀. The biggest time T_(c)is the closest time to the originally requested time interval thatsatisfies the constraints. At block 1220, the smallest time T_(d) may bedetermined in a manner similar to that which is described with regard toblock 1010, which is directed to determining a smallest time in apositively elastic time interval. The smallest time T_(d) may berepresented as T₁<T_(d)<=T_(a)+Q. The smallest time T_(d) is the closesttime to the originally requested time interval that satisfies theconstraints.

At decision diamond 1230, it is determined whether a biggest time T_(c)or a smallest time T_(d) is found within the elastic time range. Atblock 1240, a biggest time T_(c) or a smallest time T_(d) may not befound within the elastic time range. In such a case, the NE may returnan indication to the requesting entity that a path cannot be foundwithin the elastic time range specified by the request. At block 1250,the time T that is the closest to the originally requested timeintervals may be determined. For example, when an NE finds a biggesttime T_(c) and a smallest time T_(d), the NE may compare a firstdistance between the biggest time T_(c) and the start time T_(a) with asecond distance between the start time T_(a) and the smallest time T_(d)to determine which time is the closest to the originally requested timeinterval. If the first distance is less than the second distance, thenthe biggest time T_(c) is closer to the original time interval than thesmallest time T_(d) and the biggest time T_(c) is assigned to the time Tand the shift left start time T₀; otherwise, the smallest time T_(d) iscloser and the smallest time T_(d) is assigned to the time T and theshift right start time T₁. When only a biggest time T_(c) is found, theNE may determine that the biggest time T_(c) is the time that is theclosest to the originally requested time interval. The NE assigns thebiggest time T_(c) to the time T and the shift left start time T₀. Whenonly a smallest time T_(d) is found, the NE may determine that smallesttime T_(d) is the time that is the closest to the originally requestedtime interval. The NE assigns the smallest time T_(d) to the time T andthe shift right start time T₁.

At block 1270, a shortest path in a network, such as the network 200,from the ingress to the egress satisfying the requested constraints inthe time interval from T to T+(T_(b)−T_(a)) is computed, for example, byemploying a CSPF algorithm. The constraint may include bandwidth,wavelengths, delays, QoS, and number of hops. For example, the NE isconfigured to compute paths in a single AS domain, such as the domains240. Thus, the computed shortest path may span a segment of the LSPwithin the AS domain of the NE.

At decision diamond 1280, it may be determined whether a shortest pathin the network that satisfies the requested constraints in the timeinterval from T to T+(T_(b)−T_(a)) is found. At block 1290, a path maybe successfully computed, and the time T and an indication of the pathmay be returned. For example, the NE may successfully find the shortestpath in the network that satisfies the constraints in the time intervalfrom T to T+(T_(b)−T_(a)). The NE may notify the requesting entity ofthe computed shortest path and the time T. From the time T, the shiftedtime interval from T to T+(T_(b)−T_(a)) is obtained. For example, the NEmay send a response to the requesting entity indicating a path for theLSP satisfying the network constraint in the shifted time interval andan in-advance reservation of network resource along the path for the LSPin the shifted time interval. When it is determined that no path isfound at block 1280, with the new shift left start time or the new shiftright start time assigned at block 1250, the method goes to block 1210and repeats the steps in block 1210 and the blocks below block 1210until the method reaches block 1290 or block 1240.

FIG. 10 is a flowchart of an embodiment of a temporal tunnel servicemethod 1300. The method 1300 is implemented by an NE such as the edgenodes 221, the internal nodes 222, and the NE 300. The method 1300 isimplemented when creating a temporal LSP, such as the LSP 150, in anetwork, such as the network 200, when a time interval is elastic withinan elastic range lower bound, such as elastic range lower bounds 751 and851, or an elastic range upper bound, such as elastic range upper bounds652 and 852. At block 1305, a request requesting creation of a temporalLSP in a network is received. For example, a NE receives a request for atemporal LSP in a network. For example, the request indicates aningress, an egress, a network constraint, a scheduled time intervalhaving a predetermined start time and a predetermined end time for thetemporal LSP to carry first traffic, and an elasticity of the scheduledtime interval. At block 1310, a shortest path from the ingress to theegress for the temporal LSP is computed by determining a minimum amountof time to shift the scheduled time interval from the start time suchthat the path satisfies the network constraint in a shifted timeinterval and the shifted time interval is positioned within the elastictime range and with the minimum time shift. At block 1315, it isdetermined whether a next hop link from the NE to a next downstream nodeon the path comprises a sufficient amount of network resources in theshifted time interval to satisfy the network constraint. In oneembodiment, a first Path message is created and sent to the NE when theshortest path that satisfies the constraints in the shifted timeinterval is computed. The first Path message comprises the ingress, theegress, the path, the constraints, and the shifted time interval. The NEdetermines whether a next hop link from the NE to a next downstream nodeon the path comprises a sufficient amount of network resources in theshifted time interval to satisfy the network constraints after receivingthe first Path message. At block 320, the NE reserves the networkresources such as the link bandwidth on the next hop link for use duringthe shifted time interval for the temporal LSP in advance of thepredetermined start time according to the network constraints tofacilitate data forwarding for the temporal LSP in the shifted timeinterval when the NE determines that the next hop link from the NE tothe next downstream node on the path comprises a sufficient amount ofnetwork resources in the shifted time interval to satisfy theconstraints. In one embodiment, the NE constructs a second Path messageaccording to the first Path message and sends the second Path message tothe next downstream node on the path to create the temporal LSP in thenetwork. The second Path message comprises the ingress, the egress, theconstraints and the shifted time interval.

It should be noted that after a temporal LSP is created, a requestingentity may request to increase a duration of a scheduled time interval,to decrease a duration of a scheduled time interval, to add a new timeinterval, or to delete a scheduled time interval. To increase a durationof a scheduled time interval, the NE may compute a path for theincreased time interval satisfying a constraint of the LSP and extendthe reservation of network resources on each link along the path for theLSP according to the increased time interval. In one embodiment, an NEmay compute a path for the time duration that is increased from thescheduled time interval along the path computed for the LSP in thescheduled time interval and reserve network resources on each link alongthe path for the LSP in the duration increased. In another embodiment,an NE may compute a path for the increased time interval including thescheduled time interval and the duration increased by sharing thenetwork resources reserved for the LSP in the scheduled time interval,release the network resources for the LSP in the scheduled time intervaland reserve network resources in the increased time interval. Todecrease a duration of a schedule time interval, an NE may releasepreviously reserved network resources on each link along the LSP in thetime duration that is removed. To add a new time interval, an NE maycompute a path for the new time interval satisfying a constraint of theLSP and reserve network resources on each link along the path for theLSP according to the new time interval. To delete a scheduled timeinterval, an NE may release previously reserved network resources oneach link along the path for the LSP in the deleted time interval.

As described above, once an existing MPLS TE LSP is set up, it isassumed to carry traffic forever until it is down. When an MPLS TE LSPtunnel is up, it is assumed that the LSP consumes its reserved networkresources forever even though the LSP may only use network resourcesduring some period of time. As a result, the network resources are notused efficiently. Moreover, a tunnel service may not be reserved orbooked in advance for a period of time or a sequence of time periods.The disclosed embodiments describe the process for initiating an MPLS TELSP in a period of time called a time interval or a sequence of timeintervals that may be elastic. It is assumed that the LSP carriestraffic during this time interval or each of these time intervals. Thusthe network resources are efficiently used. More importantly, some newservices may be provided. For example, a consumer may book a tunnelservice in advance for a given time interval. Tunnel services may bescheduled.

A user configures a temporal LSP with a time interval or a sequence oftime intervals. A simple time interval is a time period from time Ta totime Tb, which may be represented as [Ta, Tb]. When an LSP is configuredwith time interval [Ta, Tb], a path satisfying the constraints for theLSP in the time interval is computed and the LSP along the path is setup to carry traffic from time Ta to time Tb. In addition to simple timeintervals, there are recurrent time intervals and elastic timeintervals. Sometimes a simple time interval is called a time interval.

When an LSP is configured with elastic time interval “[Ta, Tb] within −Pand Q”, a path is computed such that the path satisfies the constraintsfor the LSP in the time period from (Ta+X) to (Tb+X) and |X| is theminimum value, wherein X is from −P to 0, 0, to P, or −P to Q. That isthat [Ta+X, Tb+X] is the time interval closest to time interval [Ta, Tb]within the elastic range. The LSP along the path is set up to carrytraffic in the time period from (Ta+X) to (Tb+X).

In one embodiment, the disclosure includes an ingress node in a network,comprising a means for receiving a request for a temporal label switchedpath (LSP) in the network, wherein the request indicates an ingressnode, an egress node, a network constraint, and a scheduled timeinterval having a predetermined start time and a predetermined end timefor the temporal LSP to carry traffic, a means for computing a shortestpath in the network for the temporal LSP, wherein the path satisfies thenetwork constraint in a shifted time interval when the request indicatesthat the time interval is elastic, and a means for reserving a networkresource for use during the shifted time interval for the temporal LSPin advance of the predetermined start time, wherein the network resourceis reserved on a link extending from the ingress node to a next hop nodeon the path, and a means for sending a path message to the next hop nodeto set up the temporal LSP in the network in the shifted time interval.

In another embodiment, the disclosure includes a method implemented in aNE, comprising a means for receiving, via a receiver, a requestrequesting creation of a temporal label switched path (LSP) in anetwork, wherein the request indicates an ingress, an egress, a networkconstraint, a scheduled time interval having an elastic range, apredetermined start time and a predetermined end time for the temporalLSP to carry first traffic in a shifted time interval within the elasticrange of the scheduled time interval, a means for computing, via aprocessor, a shortest path for the temporal LSP by determining a minimumamount of time to shift the scheduled time interval from the start timesuch that the path satisfies the network constraint in a shifted timeinterval and the shifted time interval is positioned within the elastictime range and with the minimum time shift, a means for determining, viathe processor, whether a next hop link from the NE to a next downstreamnode on the shortest path comprises a sufficient amount of networkresources in the shifted time interval to satisfy the networkconstraint, and a means for reserving, via the processor, the networkresource on the next hop link for use during the shifted time intervalfor the temporal LSP in advance of the predetermined start timeaccording to the network constraint to facilitate data forwarding forthe temporal LSP in the shifted time interval when the next hop linkfrom the NE to the next downstream node on the shortest path comprisesthe sufficient amount of network resources in the shifted time intervalto satisfy the network constraint.

In yet another embodiment, the disclosure includes an apparatus,comprising a means for receiving a request requesting creation of atemporal label switched path (LSP) in a network, wherein the requestindicates an ingress, an egress, a network constraint and a scheduledtime interval having an elastic range, a predetermined start time and apredetermined end time for the temporal LSP to carry traffic in ashifted time interval within the elastic range of the scheduled timeinterval, a means for computing a shortest path for the temporal LSP bydetermining a minimum amount of time to shift the scheduled timeinterval from the start time such that the path satisfies the networkconstraint in a shifted time interval and the shifted time interval ispositioned within the elastic time range and with the minimum timeshift, a means for determining whether a next hop link from theapparatus to a next downstream node on the shortest path comprises asufficient amount of network resources in the shifted time interval tosatisfy the network constraint, and a means for reserving the networkresource on the next hop link for use during the shifted time intervalfor the temporal LSP in advance of a predetermined start time accordingto the network constraint to facilitate data forwarding for the temporalLSP in the shifted time interval.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods might beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted, or not implemented.

In addition, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as coupled or directly coupled orcommunicating with each other may be indirectly coupled or communicatingthrough some interface, device, or intermediate component whetherelectrically, mechanically, or otherwise. Other examples of changes,substitutions, and alterations are ascertainable by one skilled in theart and could be made without departing from the spirit and scopedisclosed herein.

What is claimed:
 1. An ingress node in a network, comprising: a receiverconfigured to receive a request for a temporal label switched path (LSP)in the network, wherein the request indicates the ingress node, anegress node, a network constraint, and a scheduled time interval havinga predetermined start time and a predetermined end time for the temporalLSP to carry traffic; a processor coupled to the receiver and configuredto: compute a shortest path in the network for the temporal LSP, whereinthe path satisfies the network constraint in a shifted time intervalwhen the request indicates that the time interval is elastic; andreserve a network resource for use during the shifted time interval forthe temporal LSP in advance of the predetermined start time, wherein thenetwork resource is reserved on a link extending from the ingress nodeto a next hop node on the path; and a transmitter coupled to theprocessor and configured to send a path message to the next hop node toset up the temporal LSP in the network in the shifted time interval. 2.The ingress node of claim 1, wherein reserving the network resourceincludes a future reservation, and wherein the network resource isreserved from a time-based traffic engineering link state database(TEDB).
 3. The ingress node of claim 1, wherein the request comprises astart time of the scheduled time interval, an end time of the scheduledtime interval, and an elastic range upper bound, wherein the elasticrange upper bound is a pre-defined amount of time by which the elastictime interval is permitted to shift positively to a later time than thestart time, wherein the processor is further configured to determine afirst time that is between a first shift start time and the elasticrange upper bound, and wherein the first shift start time is the starttime, wherein the first time is the only time between the first shiftstart time and the first time that has a link in a time-based trafficengineering database (TEDB) that satisfies the network constraint in afirst time interval from the first time for a duration from the starttime to the end time, and wherein for times between the first shiftstart time and the first time the link does not satisfy the networkconstraint from each of the times for the duration.
 4. The ingress nodeof claim 3, wherein the processor is further configured to determine theshortest path from the ingress node to the egress node in the TEDBsatisfying the network constraint in the first time interval when thefirst time is found.
 5. The ingress node of claim 3, wherein when nopath is found from the ingress node to the egress node in the TEDBsatisfying the network constraint in the first time interval, theprocessor is further configured to: determine a second time that isbetween a second shift start time and the elastic range upper bound, andwherein the second shift start time is the first time, wherein thesecond time is the only time between the second shift start time and thesecond time that has a link in the TEDB that satisfies the networkconstraint in a second time interval from the second time for theduration from the start time to the end time, and wherein for timesbetween the second shift start time and the second time the link doesnot satisfy the network constraint from each of the times for theduration; and determine the shortest path from the ingress node to theegress node in the TEDB satisfying the network constraint in the secondtime interval when the second time is found.
 6. The ingress node ofclaim 1, wherein the request comprises a start time of the scheduledtime interval, an end time of the scheduled time interval, and anelastic range lower bound, wherein the elastic range lower bound is apre-defined amount of time by which the elastic time interval ispermitted to shift negatively to an earlier time than the start time,wherein the processor is further configured to determine a third timethat is between the start time and the elastic range lower bound,wherein the third time is the only time between the start time and thethird time that has a link in a time-based traffic engineering database(TEDB) that satisfies the network constraint in a third time intervalfrom the third time for a duration from the start time to the end time,and wherein for times between the third time and the start time the linkdoes not satisfy the network constraint from each of the times for theduration.
 7. The ingress node of claim 1, wherein the request comprisesa start time of the scheduled time interval, an end time of thescheduled time interval, and an elastic range lower bound, and anelastic range upper bound, wherein the elastic range lower bound is apre-defined amount of time by which the elastic time interval ispermitted to shift negatively to an earlier time than the start time,wherein the elastic range upper bound is a pre-defined amount of time bywhich the elastic time interval is permitted to shift positively to alater time than the start time, wherein the processor is furtherconfigured to: compute a first time that is between the start time andthe elastic range upper bound; compute a second time that is between theelastic range lower bound and the start time; and determine a closertime of the first time and the second time, wherein the closer time is atime that is closer to the start time and has a link in a time-basedtraffic engineering database (TEDB) that satisfies the networkconstraint in a first time interval from the closer time for a durationfrom the start time to the end time, and wherein for times between thestart time and the closer time the link does not satisfy the networkconstraint from each of the times for the duration.
 8. The ingress nodeof claim 1, wherein the request comprises a start time for the timeinterval and an elastic time range for the time interval, and whereinthe processor is further configured to: compute the path for the LSP bydetermining a minimum amount of time to shift the time interval from thestart time such that the path satisfies the network constraint in theshifted time interval and the shifted time interval is positioned withinthe elastic time range; and initiate setup of the LSP in the shiftedtime interval to enable the LSP to carry traffic in the shifted timeinterval.
 9. The ingress node of claim 1, wherein the processor isfurther configured to initiate setup of the LSP in the elastic timeinterval by: sending, via the transmitter, a Path message to a nodealong the path to initiate the creation of the LSP at a beginning of theshifted time interval; and sending, via the transmitter, a PathTearmessage to a node along the path to initiate the deletion of the LSP atan end of the shifted time interval.
 10. A method implemented in anetwork element (NE), comprising: receiving, via a receiver, a requestrequesting creation of a temporal label switched path (LSP) in anetwork, wherein the request indicates an ingress, an egress, a networkconstraint, a scheduled time interval having an elastic range, apredetermined start time and a predetermined end time for the temporalLSP to carry first traffic in a shifted time interval within the elasticrange of the scheduled time interval; computing, via a processor, ashortest path for the temporal LSP by determining a minimum amount oftime to shift the scheduled time interval from the start time such thatthe path satisfies the network constraint in a shifted time interval andthe shifted time interval is positioned within the elastic time rangeand with the minimum time shift; determining, via the processor, whethera next hop link from the NE to a next downstream node on the shortestpath comprises a sufficient amount of network resources in the shiftedtime interval to satisfy the network constraint; and reserving, via theprocessor, the network resource on the next hop link for use during theshifted time interval for the temporal LSP in advance of thepredetermined start time according to the network constraint tofacilitate data forwarding for the temporal LSP in the shifted timeinterval when the next hop link from the NE to the next downstream nodeon the shortest path comprises the sufficient amount of networkresources in the shifted time interval to satisfy the networkconstraint.
 11. The method of claim 10, further comprising: sending, viathe processor, a first Path message to itself, wherein the Path messagecomprises the path, the network constraint, and the shifted timeinterval; receiving, via the processor, the first Path message;generating, via the processor, a second Path message according to thefirst Path message to indicate the shifted time interval; and sending,via a transmitter of the NE, the second Path message to the nextdownstream node to request the creation of the temporal LSP in thenetwork in the shifted time interval.
 12. The method of claim 10,wherein the request comprises a start time of the scheduled timeinterval, an end time of the scheduled time interval, and an elasticrange upper bound, wherein the elastic range upper bound is apre-defined amount of time by which the elastic time interval ispermitted to shift positively to a later time than the start time,wherein the method further comprises determining a first time that isbetween a first shift start time and the elastic range upper bound, andwherein the first shift start time is the start time, wherein the firsttime is the only time between the first shift start time and the firsttime that has a link in a time-based traffic engineering database (TEDB)that satisfies the network constraint in a first time interval from thefirst time for a duration from the start time to the end time, andwherein for times between the first shift start time and the first timethe link does not satisfy the network constraint from each of the timesfor the duration.
 13. The method of claim 12, wherein when no path isfound from the ingress to the egress in the TEDB satisfying the networkconstraint in the first time interval, the method further comprises:determining a second time that is between a second shift start time andthe elastic range upper bound, wherein the second shift start time isthe first time, wherein the second time is the only time between thesecond shift start time and the second time that has a link in the TEDBthat satisfies the network constraint in a second time interval from thesecond time for the duration from the start time to the end time, andwherein for times between the second shift start time and the secondtime the link does not satisfy the network constraint from each of thetimes for the duration; and determining the shortest path from theingress to the egress in the TEDB satisfying the network constraint inthe second time interval when the second time is found.
 14. The methodof claim 10, wherein the request comprises a start time of the scheduledtime interval, an end time of the scheduled time interval, and anelastic range lower bound, wherein the elastic range lower bound is apre-defined amount of time by which the elastic time interval ispermitted to shift negatively to an earlier time than the start time,wherein the method further comprises: determining a third time that isbetween the elastic range lower bound and the start time, wherein thethird time is the only time between the third time and the start timethat has a link in a time-based traffic engineering database (TEDB) thatsatisfies the network constraint in a third time interval from the thirdtime for a third duration from the start time to the end time, andwherein for times between the third time and the start time the linkdoes not satisfy the network constraint from each of the times for theduration; and determining the shortest path from the ingress to theegress in the TEDB satisfying the network constraint in the third timeinterval when the third time is found.
 15. The method of claim 10,wherein the request comprises a start time of the scheduled timeinterval, an end time of the scheduled time interval, and an elasticrange lower bound, and an elastic range upper bound, wherein the elasticrange lower bound is a pre-defined amount of time by which the elastictime interval is permitted to shift negatively to an earlier time thanthe start time, wherein the elastic range upper bound is a pre-definedamount of time by which the elastic time interval is permitted to shiftpositively to a later time than the start time, wherein the methodfurther comprises: determining a first time that is between the starttime and the elastic range upper bound; determining a second time thatis between the start time and the elastic range lower bound; determininga closer time of the first time and the second time, wherein the closertime is a time that is closer to the start time and has a link in atime-based traffic engineering database (TEDB) that satisfies thenetwork constraint in a first time interval from the closer time for aduration from the start time to the end time, and wherein for timesbetween the start time and the closer time the link does not satisfy thenetwork constraint from each of the times for the duration; anddetermining the shortest path from the ingress to the egress in the TEDBsatisfying the network constraint in the first time interval when thefirst time is found.
 16. An apparatus, comprising: a receiver configuredto receive a request requesting creation of a temporal label switchedpath (LSP) in a network, wherein the request indicates an ingress, anegress, a network constraint and a scheduled time interval having anelastic range, a predetermined start time and a predetermined end timefor the temporal LSP to carry traffic in a shifted time interval withinthe elastic range of the scheduled time interval; a processor coupled tothe receiver and configured to: compute a shortest path for the temporalLSP by determining a minimum amount of time to shift the scheduled timeinterval from the start time such that the path satisfies the networkconstraint in a shifted time interval and the shifted time interval ispositioned within the elastic range and with the minimum time shift;determine whether a next hop link from the apparatus to a nextdownstream node on the shortest path comprises a sufficient amount ofnetwork resources in the shifted time interval to satisfy the networkconstraint; and reserve the network resource on the next hop link foruse during the shifted time interval for the temporal LSP in advance ofa predetermined start time according to the network constraint tofacilitate data forwarding for the temporal LSP in the shifted timeinterval.
 17. The apparatus of claim 16, wherein the request furthercomprises a start time of the scheduled time interval, a stop time ofthe scheduled time interval, and an elastic upper range bound of thescheduled time interval, wherein the elastic range upper bound is apre-defined amount of time by which the elastic time interval ispermitted to shift positively to a later time than the start time,wherein the processor is further configured to determine a first timethat is between a first shift start time and the elastic range upperbound, and wherein the first shift start time is the start time, whereinthe first time is the only time between the first shift start time andthe first time that has a link in a time-based traffic engineeringdatabase (TEDB) that satisfies the network constraint in a first timeinterval from the first time for a duration from the start time to theend time, and wherein for times between the first shift start time andthe first time the link does not satisfy the network constraint fromeach of the times for the duration.
 18. The apparatus of claim 17,wherein when no path is found from the ingress to the egress in the TEDBsatisfying the network constraint in the first time interval, theprocessor is further configured to: determine a second time that isbetween a second shift start time and the elastic range upper bound, andwherein the second shift start time is the first time, wherein thesecond time is the only time between the second shift start time and thesecond time that has a link in the TEDB that satisfies the networkconstraint in a second time interval from the second time for theduration from the start time to the end time, and wherein for timesbetween the second shift start time and the second time the link doesnot satisfy the network constraint from each of the times for theduration; and determine the shortest path from the ingress to the egressin the TEDB satisfying the network constraint in the second timeinterval when the second time is found.
 19. The apparatus of claim 16,wherein the request further comprises a start time of the scheduled timeinterval, a stop time of the scheduled time interval, and an elasticlower range bound of the scheduled time interval, wherein the elasticrange lower bound is a pre-defined amount of time by which the elastictime interval is permitted to shift negatively to an earlier time thanthe start time, wherein the processor is further configured to determinea third time that is between the elastic range lower bound and a thirdshift start time, wherein the third shift start time is the start time,wherein the third time is the only time between the third time and thestart time that has a link in a time-based traffic engineering database(TEDB) that satisfies the network constraint in a third time intervalfrom the third time for a duration from the start time to the stop time,and wherein for times between the third time and the start time the linkdoes not satisfy the network constraint from each of the times for theduration.
 20. The apparatus of claim 19, wherein when no path is foundfrom the ingress to the egress in the TEDB satisfying the networkconstraint in the third time interval, the processor is furtherconfigured to: determine a fourth time that is between a fourth shiftstart time and the elastic range lower bound, wherein the fourth shiftstart time is the third time and the fourth time is the only timebetween the fourth shift start time and the fourth time that has a linkin the TEDB that satisfies the network constraint in a fourth timeinterval from the fourth time for the duration from the start time tothe stop time, wherein for times between the fourth shift start time andthe fourth time the link does not satisfy the network constraint fromeach of the times for the duration; and determine the shortest path fromthe ingress to the egress in the TEDB satisfying the network constraintin the fourth time interval when the fourth time is found.